Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(performance): Add performance config documentation #500

Merged
merged 2 commits into from
Dec 20, 2016

Conversation

TheLarkInn
Copy link
Member

Fixes #435

- thelarkinn
---

The options allows you to control how webpack notifies you of assets and entrypoints that exceed a specific file limit.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/The/These/

}
```

A warning will be displayed notifying you of a large asset. We recommend something like this for development environments.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's say you are inlining assets during development, missing minification etc., wouldn't this yield warnings even if they aren't relevant? Isn't the best value in production build?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but also gives perspective to users as they are developing.

If a bundle grows from 200->350kb after a certain feature, I'd want to know specifically about it while developing so I can trace my steps back a few changes and investigate more into what is causing the bloat.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright. I guess it takes more experience with the feature for me to tell any better. Hitting the limits is very easy by inlining just a few images.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Developing the last thing I'd like is to be caught of guard after x hours of development to see errors because of size stuff I could maybe have caught in the act.

Again these are just hypothetical/estimates etc.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes true. Maybe that's where they could filter assets, etc.

I mean at the most these are recommendations but I 100% agree where you are coming from.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to have something like --json kind of flag for the perf data? Can you get it in JSON to track?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aww that would actually be a really cool feature but the log might be built. I'm going to add that to the original issue.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be big*

@TheLarkInn
Copy link
Member Author

Any other looks? Want to get this in since Perf is in now.

@TheLarkInn
Copy link
Member Author

Any other objections? Going to merge this.

@bebraw
Copy link
Contributor

bebraw commented Dec 20, 2016

Yeah, merge. More tweaks can be done in separate PRs.

@TheLarkInn TheLarkInn merged commit 369d381 into develop Dec 20, 2016
@bebraw bebraw deleted the feature/performance_configuration branch January 24, 2017 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants